DRAFT: migrate refsi_tutorial MRs #739
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
coldav
reviewed
Apr 8, 2025
| # Note : Refsi is not as complete as riscv (e.g. runtime linking) | ||
| # so disable offline kernel tests | ||
| offline_kernel_tests: OFF | ||
| llvm_install_dir: /refsi_tutorial/build/llvm |
There was a problem hiding this comment.
it might not make sense to be the same directory to be honest - maybe $GITHUB_WORKSPACE/refsi_tutorial?
coldav
reviewed
Apr 30, 2025
|
|
||
|
|
||
| # Based on: mr-ubuntu-gcc-x86_64-refsi-tutorial-start | ||
| run-ubuntu-gcc-x86_64-refsi-tutorial-start: |
There was a problem hiding this comment.
I think perhaps this could come after, if that helps to get the other one in.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Provide a brief overview of what your changes do, summarizing their effects
and consequences.
Reason for change
Describe how the current behaviour of the project is causing problems for you
or is otherwise unsatisfactory for your use case.
Description of change
Describe the intended behaviour your changes are meant to introduce to the
project and explain how they resolve the problem stated above. Detail any
relevant changes that may affect other users of the project, such as
compilation options, runtime flags, expected inputs and outputs, API entry
points, etc.
If you have added new testing, provide details on what tests you have added
and what the purpose of them is.
Anything else we should know?
If there's any other relevant information we should know that may help us in
understanding and verifying your patch, please include it here.
Checklist